_nnnn_eeee_tttt_bbbb_uuuu_ffff is described in _iiii_nnnn_tttt_rrrr_oooo(3N). In _uuuu_nnnn_iiii_tttt_dddd_aaaa_tttt_aaaa, _aaaa_dddd_dddd_rrrr specifies the
protocol address of the destination user, _oooo_pppp_tttt identifies protocol-
specific options that the user wants associated with this request, and
_uuuu_dddd_aaaa_tttt_aaaa specifies the user data to be sent. The user may choose not to
specify what protocol options are associated with the transfer by setting
the _llll_eeee_nnnn field of _oooo_pppp_tttt to zero. In this case, the provider may use default
options.
If the _llll_eeee_nnnn field of _uuuu_dddd_aaaa_tttt_aaaa is zero, and the sending of zero bytes is not
supported by the underlying transport provider, _tttt______ssss_nnnn_dddd_uuuu_dddd_aaaa_tttt_aaaa will return -1
with _tttt______eeee_rrrr_rrrr_nnnn_oooo set to _TTTT_BBBB_AAAA_DDDD_DDDD_AAAA_TTTT_AAAA.
By default, _tttt______ssss_nnnn_dddd_uuuu_dddd_aaaa_tttt_aaaa operates in synchronous mode and may wait if flow
control restrictions prevent the data from being accepted by the local
transport provider at the time the call is made. However, if _OOOO______NNNN_DDDD_EEEE_LLLL_AAAA_YYYY or
_OOOO______NNNN_OOOO_NNNN_BBBB_LLLL_OOOO_CCCC_KKKK is set (via _tttt______oooo_pppp_eeee_nnnn or _ffff_cccc_nnnn_tttt_llll), _tttt______ssss_nnnn_dddd_uuuu_dddd_aaaa_tttt_aaaa will execute in
asynchronous mode and will fail under such conditions.
If _tttt______ssss_nnnn_dddd_uuuu_dddd_aaaa_tttt_aaaa is issued from an invalid state, or if the amount of data
specified in _uuuu_dddd_aaaa_tttt_aaaa exceeds the _TTTT_SSSS_DDDD_UUUU size as returned in the _tttt_ssss_dddd_uuuu field of
the _iiii_nnnn_ffff_oooo argument of _tttt______oooo_pppp_eeee_nnnn or _tttt______gggg_eeee_tttt_iiii_nnnn_ffff_oooo, the provider will generate an
_EEEE_PPPP_RRRR_OOOO_TTTT_OOOO protocol error. (See _TTTT_SSSS_YYYY_SSSS_EEEE_RRRR_RRRR below.) If the state is invalid,
this error may not occur until a subsequent reference is made to the
transport endpoint.
This function resides within both the X/Open compliant _llll_iiii_bbbb_xxxx_nnnn_eeee_tttt and the
On failure, _tttt______eeee_rrrr_rrrr_nnnn_oooo may be set to one of the following:
_TTTT_BBBB_AAAA_DDDD_FFFF The specified file descriptor does not refer to a
transport endpoint.
_TTTT_FFFF_LLLL_OOOO_WWWW _OOOO______NNNN_DDDD_EEEE_LLLL_AAAA_YYYY or _OOOO______NNNN_OOOO_NNNN_BBBB_LLLL_OOOO_CCCC_KKKK was set, but the flow control
mechanism prevented the transport provider from
accepting data at this time.
_TTTT_NNNN_OOOO_TTTT_SSSS_UUUU_PPPP_PPPP_OOOO_RRRR_TTTT This function is not supported by the underlying
transport provider.
_TTTT_OOOO_UUUU_TTTT_SSSS_TTTT_AAAA_TTTT_EEEE If ______XXXX_OOOO_PPPP_EEEE_NNNN______SSSS_OOOO_UUUU_RRRR_CCCC_EEEE is defined and _tttt______ssss_nnnn_dddd_uuuu_dddd_aaaa_tttt_aaaa() is issued
in the wrong sequence on the transport endpoint
referenced by _ffff_dddd, the _TTTT_OOOO_UUUU_TTTT_SSSS_TTTT_AAAA_TTTT_EEEE error value is returned
within the variable _tttt______eeee_rrrr_rrrr_nnnn_oooo.
_TTTT_SSSS_YYYY_SSSS_EEEE_RRRR_RRRR A system error has occurred during execution of this
function.
_TTTT_BBBB_AAAA_DDDD_DDDD_AAAA_TTTT_AAAA There are multiple conditions which could cause this
_tttt______eeee_rrrr_rrrr_nnnn_oooo to be generated. One condition is: _nnnn_bbbb_yyyy_tttt_eeee_ssss is
zero and sending zero bytes is not supported by the
transport provider. Another condition is: if
______XXXX_OOOO_PPPP_EEEE_NNNN______SSSS_OOOO_UUUU_RRRR_CCCC_EEEE is defined and a single send was
attempted specifying a _TTTT_SSSS_DDDD_UUUU greater than that specified
by the current values of the _TTTT_SSSS_DDDD_UUUU field in the _iiii_nnnn_ffff_oooo